@vladchuk To help better explain the problem and solution, please provide a complete example Appcast file showing the current usage with the issue, and also another example showing the solution.

Currently, only the following is possible:

<rss version="2.0" xmlns:sparkle="http://www.andymatuschak.org/xml-namespaces/sparkle">
    <channel>
        <title>My App</title>
        <item>
            <enclosure sparkle:version="2.3.0" url="https://downloads/application-install-2.3.0.exe"
                sparkle:os="windows" />
        </item>
        <item>
            <enclosure sparkle:version="2.3.0" url="https://downloads/application-2.3.0.apk"
                sparkle:os="android" />
        </item>
    </channel>
</rss>

This allows one to distribute either a single Android binaries (ABI) or a fat apk, containing multiple ABI and thus forcing the client to needlessly download and use the file a few times bigger than necessary. This works OK for a single target ABI.

But what if one needs to support more than one? It is generally recommended to build specific APKs which contain a single ABI, targeting a specific device and sparing the client "the dead weight" of the ones it can't use. The following affords such precise and efficient targeting, since now the APKs contains only what necessary for each client:

<rss version="2.0" xmlns:sparkle="http://www.andymatuschak.org/xml-namespaces/sparkle">
    <channel>
        <title>My App</title>
        <item>
            <enclosure sparkle:version="2.3.0" url="https://downloads/application-install-2.3.0.exe"
                sparkle:os="windows" />
        </item>
        <item>
            <enclosure sparkle:version="2.3.0" url="https://downloads/application-v7a-2.3.0.apk"
                sparkle:os="android" abi="armeabi-v7a" />
        </item>
        <item>
            <enclosure sparkle:version="2.3.0" url="https://downloads/application-v8a-2.3.0.apk"
                sparkle:os="android" abi="arm64-v8a" />
        </item>
    </channel>
</rss>

Android is given an example, but the situation is applicable to other platforms, for example Windows 32 vs 64 bit, etc. In fact, it's even worse, since it's impossible to combine different binaries in a single file, like for Android.

I hope this makes it clear what problem this addition would solve.

@vladchuk I like this idea and thanks for submitting. However, abi is an Android only concept that cannot be properly used on other OSes like Windows. How about a name that would work across all OSes and platforms?

I probably misled you by providing a lopsided (Android) example. ABI (Application Binary Interface) is actually a descriptive, universal and widely used concept. Here is an excerpt from an AI (Bard) inquiry:

"Application binary interfaces (ABIs) are applicable to a wide variety of platforms, including:

Operating systems: ABIs are used to define the interaction between applications and the operating system. For example, the Linux ABI defines how applications can interact with the Linux kernel.
Programing languages: ABIs can also be used to define the interaction between programs written in different programming languages. For example, the C++ ABI defines how C++ programs can interact with programs written in C.
Hardware architectures: ABIs can also be used to define the interaction between software and hardware. For example, the ARM ABI defines how software can interact with ARM processors.

Here are some specific examples of platforms where ABIs are used:

Windows: The Windows API is an ABI that defines how applications can interact with the Windows operating system.
macOS: The macOS API is an ABI that defines how applications can interact with the macOS operating system.
Android: The Android NDK (Native Development Kit) provides an ABI that defines how applications can interact with the Android operating system.
iOS: The Apple Developer Documentation provides an ABI that defines how applications can interact with the iOS operating system.
Linux: The Linux Standard Base (LSB) provides an ABI that defines how applications can interact with the Linux kernel.

In general, ABIs are used whenever there is a need for software from different sources to communicate with each other. This includes applications written in different programming languages, applications running on different operating systems, and applications running on different hardware architectures."

You can easily expand on this research if you like (with Bard, ChatGPT or simply Googling).

Ultimately, I think that calling it anything other than ABI would be quite confusing, while using it as is conveys the meaning very accurately and succinctly.

Hi @vladchuk I would like to get this PR merged, but first the conflicts need to be resolved, and the extra files need to be removed. If you are still interested in getting this change into this project, can you make those changes?